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

TickFlow Field · for payment terminals and field devices

Terminal down?One tap. Diagnosed, fixed and verified, remotely.

A cashier taps Report a problem. Card data is redacted on the terminal, a ticket with evidence opens in under a minute, AI finds the cause, and a signed playbook fixes it. Anything risky waits for your approvers.

Book a demoSee how it works
Tap → ticket
< 60 s
Card data sent
0 PANs
Fixed with no visit
≥ 30 %

Pilot targets we agree with you up front, not results.

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
Field gatewaynorthwind-bank
14:17:02check-inT-06 · 212 bytes · dormant, nothing else sent
14:32:07report.tapDowntown T-06 · PAX A920 Pro · “Card reader”
14:32:09redact.edgeI/Reader session open usb=1-1.2E/Pay auth pan=4111 1111 1111 1111[PAN] amt=42.50D/Receipt to=dana.k@northwind.ca[EMAIL]E/Reader E-R07 timeout after usb re-enumerationredaction record · card 1 · e-mail 1 · counts only
14:32:46ticketFR-1001 opened · tap → ticket 39 s
14:32:58triageReader session not re-opened after USB reset78%Outdated reader firmware 2.1.431%Known issue · cluster of 4 reports this week
14:33:40playbookapp.restart · impact change · ran on its ownsigned · waited for idle · on the ledger #18,234
14:33:51verifiedhealth check passedVisit avoided · CA$185
  • PAX A920 Pro
  • Sunmi V2s
  • Ingenico AXIUM DX8000
  • Verifone T650p
  • PAX A77
  • Sunmi T2s kiosk
  • Windows POS
  • macOS back office
  • Linux kiosks
  • Web POS in Chrome
  • Android SDK
  • React Native SDK
  • iOS, inside your app
  • PAX A920 Pro
  • Sunmi V2s
  • Ingenico AXIUM DX8000
  • Verifone T650p
  • PAX A77
  • Sunmi T2s kiosk
  • Windows POS
  • macOS back office
  • Linux kiosks
  • Web POS in Chrome
  • Android SDK
  • React Native SDK
  • iOS, inside your app

From tap to fixed, in one loop

What happens in the next 104 seconds.

One report from a PAX A920 Pro at a Northwind Bank branch, start to finish. Scroll through it.

  1. 01 Report

    The cashier taps one button.

    The Field agent floats a Report a problem button over the payment app. One tap captures the screen, the last 30 minutes of logs from an encrypted on-device buffer, the device’s state and recent errors. No form, no phone call, no “it just stopped working”.

    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

  2. 02 Redact

    Card numbers become [PAN] before they leave the terminal.

    Redaction runs on the device: card numbers, track data, secrets, e-mails and phone numbers are replaced by tokens before anything is sent. The same rules run on every kind of device, and the server checks every report again. Anything that still looks like card data is held back and we are alerted.

    logs/app.log · on the terminal, before upload4 secrets → tokens
    14:31:52.118 I/Reader  usb device 1-1.2 attached, session open
    14:31:58.402 D/Pay     auth start pan=4111 1111 1111 1111[PAN] amt=42.50 CAD
    14:32:01.007 W/Reader  usb re-enumeration (1-1.2 → 1-1.3)
    14:32:01.311 D/Pay     retry fallback track2=5454545454545454=2712[TRACK2]
    14:32:02.950 D/Sync    Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJ0aWQiOiJudyJ9.Qm9zc2E[JWT]
    14:32:03.020 D/Receipt e-mail copy to dana.k@northwind.ca[EMAIL]
    14:32:04.775 E/Reader  E-R07 read timeout: session handle stale
    
    redaction record{ "pci.pan": 1, "pci.track2": 1, "secret.jwt": 1, "pii.email": 1 }counts only · never the values
  3. 03 Ticket

    A ticket with the evidence attached, in 39 seconds.

    The bundle uploads over an outbound connection, resumes if the network drops, and files a numbered ticket with the screenshot, logs, device state and timeline. Your support desk sees the device, not a description of it. Illustrative timing from the demo fleet; the pilot target is under 60 seconds.

    FR-1001newtap → ticket 39 s

    Card reader not responding

    Downtown T-06 · PAX A920 Pro · Android 10 · Northwind Pay 5.12.0 @ 1a2b3c4

    screens/2 screenshotslogs/3 files · 30 minstate.jsonbattery, network, peripheralsredaction record4 hits · counts only
    0 scaptured 4 s · redacted 1 s · uploaded 31 s · filed 3 s
  4. 04 Triage

    Known issues first. Then AI, reading the logs as data.

    Field extracts error codes, fingerprints the report and matches it against the rest of your fleet. Only then does a model assess what is left, with ranked causes and the log lines behind each. Device text never enters a prompt as instructions: the model reads it through tools, delimited, as data.

    1. Stage 0 · extracterror codes E-R07, usb re-enumeration, reader firmware 2.1.4
    2. Stage 1 · fingerprintmatches cluster clu_014 · 4 reports from 3 stores this week
    3. Stage 2 · AI assessmentReader session not re-opened after USB reset 78%Outdated reader firmware 2.1.4 31%

    evidence logs/app.log:1182 · logs/logcat.txt:3301 · read by the AI as evidence, never as instructions.

  5. 05 Fix

    A signed playbook fixes it. Risky ones need two keys.

    Fixes are named playbooks with typed parameters, never shell commands. Your policy decides by impact: low-risk changes run on their own, a reboot needs one approver, wiping data needs two different people. Nothing runs during a payment.

    • readdiag.network_testruns on its own
    • changeapp.restartruns on its own · known issue
    • disruptivedevice.rebootone approval
    • destructiveapp.clear_datatwo people
    destructive · needs 2 peopleapp.clear_dataon Suburbs T-11
    Northwind BankDana K. approves
    and
    OrthoplexEli E. approves
    ✓Approval signer re-checks both votes and signs with its own key. The terminal refuses the command without that signature.

    Requested by Uma U. — who cannot approve her own request.

  6. 06 Verified

    Verified on the device. The visit never happens.

    Every playbook names a check: the app reaches its home screen, the host answers, the error is gone from a fresh capture. The ticket closes with what was done, who approved it and the ledger entry that proves it.

    health check passedfresh 5-min buffer: E-R07 gone · reader session open
    Visit avoidedCA$185at Northwind’s rate per truck roll

    If the check fails: the rollback runs, the ticket says “fix failed” and a person takes over. Two failed automatic fixes on one device pause automation on it.

Product tour

Now click through it yourself.

The same report, in the product: the fleet overview, Downtown T-06, its evidence, the approval and the ledger. Switch between what your team sees and what our engineers see.

The customer portal's overview: reports, how each ended, approvals waiting and fleet health by store.

Loading the interactive tour…

The fleet view

Hundreds of terminals. You see the few that need you.

Every square is a device. When one reports, Field checks whether its neighbours have the same fault, fixes the cluster once, and shows you the result by store: what fixed itself, what waited for an approval, what went to an engineer.

reports · 30 days
8686
fixed with no one involved
4141%
median tap → ticket
5454s
visits avoided · at CA$185
CA$9,065CA$9,065

Illustrative figures from the demo dataset, not customer results.

Vancouver · Toronto · Pearson · Montréal

How every report ended86 reports · 30 days · illustrative demo fleet
04812day 1day 11day 21today
  • Auto-fixed 35
  • Fixed after approval 14
  • With an engineer 14
  • No fault found 23
healthyattentioncriticalreportingfixedclick a square

Fleet intelligence Rolling out

It gets smarter with every fix.

Your engineers confirm or correct each root cause. Confirmed causes become known issues, so the next terminal with the same fault is matched on arrival and fixed under the same approval rules.

  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
  • One board for one problem

    The same fault across models, firmware, app versions and sites, grouped as one cluster with one fix.

  • Regression watch

    Right after a rollout, Field notices when reports start to rise and can pause the rollout before it reaches everyone.

  • Evidence before the calls

    When an issue starts to spread, Field asks the next devices for evidence, so the fix is ready before the phones ring.

  • A savings report for leadership

    Each month: visits avoided, time to fix, what fixed itself and what needed people. Health trends across the fleet.

Who it is for

For whoever pays when a terminal stops.

  • Banks & acquirers

    Every “terminal not working” call becomes phone triage or a truck roll at CA$150–300+.

    Evidence-backed tickets, remote fixes your policy controls, and fewer visits to merchants.

    CA$185a visit, at the demo rate

  • ISOs & POS resellers

    Support costs eat margin, and you cannot see the merchant's device.

    A support desk that sees the device: screenshots, logs and state behind every call.

    30 minof logs on every report

  • Retail & QSR chains

    Store staff cannot describe the problem; IT cannot reproduce it.

    One-tap capture at the counter and AI triage that groups the same fault across stores.

    1 tapfrom the cashier

  • Kiosk & self-service operators

    Devices fail unattended, and nobody is there to press anything.

    Remote-triggered capture and playbooks with verification, staged across the fleet.

    5 %blast-radius cap per hour

Fits your service desk

The diagnosis lands where your team already works.

A Field report can open as an incident or a ticket in your own service desk, with an evidence summary, the likely cause and a link back. When an agent replies or moves it on, Field hears about it. Nobody copies anything across.

  • works withServiceNowRolling out
  • works withZendeskRolling out
  • andMore on requestOn request
What syncs, and the rest of your stack
FieldFR-1001
Card reader not respondingDowntown T-06 · lane 2Likely cause reader session not re-openednewin progress · syncedfrom your desk“Approved for tonight’s window.”
report · summary · linkstatus · replies
Your service deskIncident #48213
Short description
Card reader not responding · Downtown T-06
Assignment
Merchant support
Evidence summary
2 screenshots · 30 min of logs · reader error after a USB reset
Field report
Open in TickFlow Field ↗
Dana K. · agentApproved for tonight’s window.
NewIn progress
Illustrative. Your desk’s own fields and workflow decide what it looks like.

Security & PCI

Designed to keep you out of PCI scope.

Field never receives card data and never touches the payment kernel or PIN entry. We write the scoping argument down for your QSA. Six rules decide every trade-off, and they win when anything conflicts with them.

Read the security model
  1. #18,229proposalapp.restart v3 · T-06 · triage 78%e57ae585…e70b
  2. #18,230policyruns on its own · change · known issueprev e57ae585…e70b → 5b399308…8741
  3. #18,231commandissued · signedprev 5b399308…8741 → 0f73dbee…79b0
  4. #18,232ackT-06 accepted · waited 4 s for idleprev 0f73dbee…79b0 → 594942d3…7507
  5. #18,233resultok · exit 0 · 3.1 sprev 594942d3…7507 → c87c69c8…06af
  6. #18,234verifyhealth check passedprev c87c69c8…06af → ecc800cf…146b

chain verified · 18,234 rows · no entry can be changed or removed

Turn the keys yourself.

Uma asked for a wipe of the payment app’s data. Try her key first. Then find the two people who can approve it.

Build on Field
destructive · needs 2 peopleapp.clear_dataon Suburbs T-11
Northwind BankDana K. approves
and
OrthoplexEli E. approves
✓Approval signer re-checks both votes and signs with its own key. The terminal refuses the command without that signature.

Requested by Uma U. — who cannot approve her own request.

  • Dormant by default

    No streaming. The device keeps its own recent evidence and sends only a small signed check-in until someone reports.

  • Redact at the edge

    Card numbers, track data, PINs and personal data are stripped on the device. The server re-checks and never relies on itself alone.

  • Outbound only

    Terminals sit behind merchant firewalls. The device always opens the connection; nothing ever connects to it.

  • Nothing arbitrary

    Remote actions are named, signed playbooks with typed parameters. No shell. A remote session is a consented, recorded last resort.

  • Four-eyes

    AI proposes, policy decides, people approve. Nobody approves their own request; destructive actions need two people.

  • Tamper-evident ledger

    Every command, approval and result is a row in an append-only, hash-chained ledger you can verify and export.

Platforms

One agent protocol. Every screen at the counter.

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

What the agent can do on each platform

The Coder

When the bug is in your app, it reads your code at the device’s commit.

A cluster of reports points at your own POS app? The Coder checks out the repository at the exact commit the terminal runs, follows the evidence into the code, writes a fix with a failing-then-passing test and opens a draft pull request. A person approves its plan first. It never merges.

  • repo northwind/pos-android @ 1a2b3c4
  • root cause templates.current is null after PAPER_OUT
  • result draft PR · patch applies cleanly · confidence 86%
The staff console's Coder run: root cause, the patch to ReceiptPrinter.kt and the draft pull request.

Proof, before you sign

We agree the targets up front. Then we measure them on your terminals.

These are pilot targets, written into the pilot plan with you. They are not results from other customers.

  1. pilot target< 60 smedian from tap to a ticket with evidence
  2. pilot target≥ 70 %of AI root causes rated correct or partly correct by your engineers
  3. pilot target≥ 30 %of reports resolved with no one involved, once remediation is on
  4. pilot target0card-data leaks found by the server re-scan
  5. pilot targetLighta dormant agent that stays out of the way of the payment app

What would it save you?

Move the sliders. The full calculator has more detail.

Open the savings calculator
devices
per 100 devices
% of reports
CA$ per truck roll
Avoided a yearCA$133,200CA$133,200
Visits avoided a year
720720
Avoided a month
CA$11,100CA$11,100

Estimate, not a quote. It assumes every report fixed remotely would otherwise have needed a visit. Subscription cost is not deducted.

Questions

What banks ask us first.

Does TickFlow Field bring our terminals into PCI DSS scope?

Field is designed to keep you out of scope. Card numbers, track data and PINs are redacted on the terminal before anything leaves it, the server checks every report again and holds back anything that still looks like card data, and the agent never touches the payment kernel or PIN entry. We document this scoping argument for your QSA; the assessment itself stays with your QSA.

Is the agent streaming data from our devices all day?

No. The agent is dormant. It keeps its own recent logs, encrypted, on the device and sends only a small signed check-in until someone reports. Evidence leaves the device only when someone taps Report a problem or an authorised person asks for a capture.

Can a remote fix interrupt a payment?

No. Every playbook that changes something waits until the terminal is idle. If the agent cannot tell whether a transaction is in progress, it waits up to the playbook's limit and then reports the fix as deferred instead of running it.

Can the AI run commands on our terminals?

No. AI triage and the Coder can only propose. Your policy decides what runs on its own, what needs one approver and what needs two. Nobody can approve their own request, and disruptive or destructive commands also need a separate approval that the service sending commands cannot produce on its own.

Which devices does it support?

Android payment terminals from PAX, Sunmi, Ingenico (AXIUM) and Verifone, Windows, macOS and Linux devices, and web POS or back-office portals through a Chrome extension. What the agent can do on Android depends on how it is installed: as a standard app, as Device Owner, or with vendor privileges.

Does it work with our service desk?

Integrations with ServiceNow and Zendesk are rolling out: a Field report opens an incident or ticket in your own service desk with an evidence summary, the likely cause and a link back, and status changes and replies flow back to Field. Webhooks and API keys connect your other tools, and more service desks are available on request.

Do we have to replace our MDM or terminal-management system?

No. Field installs through your MDM, EMM or the vendor's terminal-management store and works alongside it. Field adds what those tools lack: a report from the person at the counter, evidence, a diagnosis and a controlled fix.

Where is our data stored, and for how long?

In Canada by default, with a per-tenant region option on Enterprise. Default retention: diagnostic bundles 30 days, the redacted search index 13 months, the action ledger 7 years. AI runs only through providers set to no training and zero or limited retention, and you can switch AI off.

What does the Coder do?

When the cause is a bug in your own app, the Coder checks out the code at the exact commit the device runs, finds the fault, writes a fix with a test and opens a draft pull request. A person approves its plan before it starts, and it never merges anything.

Put a Report button on every 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.