POST /transaction/override — Override rounding

When a rounding outcome needs to be corrected after the fact — due to a customer dispute, a pricing error, or a system issue — a manager can apply an override. You submit the target transaction ID, the authorizing employee’s identity, a reason code, and the corrected cash total. The engine creates an immutable override audit record with its own hash, linking it to the original transaction. Override records are surfaced in the override report and are included in the merchant’s fraud risk profile.

Endpoint

POST https://api.centsless.org/api/v1/transaction/override

Authentication

string

required

Your merchant or partner API key.

Request body

string

required

The ID of the transaction to override (e.g., TXN-2026-04-14-A82C2EAA).

string

required

The ID of the employee authorizing the override (e.g., EMP-001).

string

required

The full name of the employee authorizing the override. Included verbatim in the audit record.

string

required

Reason code for the override. One of: customer-request, manager-discretion, pricing-error, system-error.

integer

required

The corrected cash total to collect, in cents. This replaces the original cash_total_cents for settlement purposes.

Example

curl -X POST https://api.centsless.org/api/v1/transaction/override \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "transaction_id": "TXN-2026-04-14-A82C2EAA",
    "employee_id": "EMP-001",
    "employee_name": "Jane Manager",
    "reason": "customer-request",
    "new_cash_total_cents": 720
  }'

Overview

Transactions

Jurisdiction

Tipping

Compliance & Audit

POST /transaction/override — Override rounding

Endpoint

Authentication

Request body

Example

​Endpoint

​Authentication

​Request body

​Example

Endpoint

Authentication

Request body

Example