How a Centsless pilot works
A pilot tests Centsless against your real transaction environment before any wider rollout. It is scoped to the jurisdictions, transaction types and evidence your team needs.
01
Scope
Agree the jurisdictions, transaction types (sales, refunds, mixed tender, payments to government) and the evidence your reviewers expect.
What we need from you
Your locations and a contact for your POS or transaction system.
02
Connect
Your transaction system sends transaction context and receives the calculated result and its decision evidence.
What we need from you
An engineering contact. Interface details are confirmed during scoping.
03
Run
Transactions in scope are resolved, calculated and recorded.
What we need from you
Access to test or limited live traffic, as agreed.
04
Review
We walk through results and the evidence record with your compliance, finance or audit team.
What we need from you
The reviewers who will rely on the record.
What you receive
- The calculated rounding result for in-scope transactions.
- A tamper-evident decision record citing the governing authority.
- A summary of which supported rules applied where.
Executable coverage is agreed in pilot scope. Tracked authorities and local policies do not establish engine support.
Security and data handling
Discussed under NDA during pilot scoping. Centsless does not claim independent security certification.
Commercial terms
Commercial terms are discussed during pilot scoping.