Skip to main content
Every completed transaction can produce a compliance receipt on demand. Receipts include state-mandated rounding disclosure language — for example, Washington SHB 2334 requires explicit disclosure of any rounding applied to a cash transaction. You choose the format based on who the receipt is for: customer-facing receipts use merchant format, internal compliance audits use audit format, and POS systems that render their own receipt UI use pos format for raw data without any markup.

​
Endpoint

GET https://api.centsless.org/api/v1/transaction/{id}/receipt

​
Authentication

​
x-api-key
string
required
Your merchant or partner API key.

​
Path parameter

​
id
string
required
The ID of the transaction to generate a receipt for (e.g., TXN-2026-04-14-A82C2EAA).

​
Query parameter

​
format
string
default:"merchant"
Receipt format. One of:
  • merchant (default) — Customer-facing receipt with rounding disclosure language as required by state law.
  • audit — Full audit receipt including the hash chain position, audit hash, and fraud score.
  • pos — Minimal format with raw cent values only, for POS systems that render their own receipt layout.

​
Example

curl "https://api.centsless.org/api/v1/transaction/TXN-2026-04-14-A82C2EAA/receipt?format=merchant" \
  -H "x-api-key: YOUR_API_KEY"