Skip to main content
Centsless tracks all post-transaction changes with employee attribution and separate audit hashes. Every override, void, and refund is recorded as an immutable entry in the hash chain — the chain links each record to the one before it, so the full correction history for any transaction is tamper-evident and auditor-readable.

Overrides

Use POST /transaction/override when a manager needs to adjust the rounded cash total on a completed transaction. The override is applied on top of the original transaction and creates its own audit record with a separate override hash. Required fields:
Each override creates an immutable audit record with a separate override hash. The original transaction record is not modified — the override is stored as a linked correction in the hash chain.

Voids

Use POST /transaction/void to cancel a transaction. The API creates a reversal record with negative amounts and maintains hash chain integrity. The original rounding delta is correctly reversed in the void record. Required fields:
The rounding delta from the original transaction is correctly reversed in the void record. Hash chain integrity is maintained — the void is appended as a new entry linked to the original transaction.

Refunds

Use POST /transaction/refund to process a partial or full refund. The engine verifies that the refund’s rounding direction correctly reverses the original transaction’s rounding delta. Required fields:
If the refund’s rounding delta doesn’t correctly reverse the original transaction’s rounding direction, the engine flags a normalization failure in the response. Normalization failures are recorded for compliance review but do not block the refund from completing.